Intelligent Network Interface

ABSTRACT

The present invention provides methods and apparatus for interconnecting disparate communications systems. A call request that originates from a communications network is directed to a network interface. The network interface consequently redirects the call request to a communications entity, such as a radio or a cellular radio system that serves the user associated with the call request. The network interface may support address translation functionality for identifying the communications entity, control conversion functionality for generating control and signaling with the communications entity, transmission content conversion functionality for converting the transmission content during the call, and security functionality for encrypting and decrypting the transmission content. Also, the present invention enables non-networking communications entities to interact with applications that are being executed on another terminal through the network, enables network management systems to manage non-networking communications entities through a network, and enables non-networking communications entities to utilize networking routing services.

This is a divisional patent application of U.S. patent application No.10/096,197 entitled “An Intelligent Network Interface” filed Mar. 12,2002 for which priority is claimed. The parent application isincorporated herein by reference in its entirety.

FIELD OF THE INVENTION

The present invention relates to interfacing a communications network toa communications entity that includes a radio or another communicationsnetwork.

BACKGROUND OF THE INVENTION

The explosive growth of telecommunications has been accompanied by thedeployment of communications systems in accordance with differenttechnologies. This fact is exemplified by wireless communications. Thereare numerous cellular radio standards, including advanced mobile phoneservice (AMPS), which is a North American standard utilizing analogtechnology, total access communications system (TACS), which is ananalog standard used in the United Kingdom, global system for mobilecommunications (GSM), which is a time division multiple technology usedin many parts of the world, and code division multiple access (CDMA),which is a spread spectrum technology. There are additional standardsfor the upcoming third generation (3G) generation of cellular radio,including cdma2000, which is an evolution of CDMA and universal mobiletelecommunications system (UMTS). In the future, new generations ofcellular radio services will occur, and thus the variety of technologieswill increase. Moreover, wireless communications also incorporatesnon-cellular radio communications including land mobile radio service(LMRS) and satellite services. One can quickly conclude that the numberof different wireless technologies is numerous and is getting largerwith the passage of time.

A user, nevertheless, expects to communicate with another userregardless of the technology that is serving the user. Substantialcapital has been invested in existing communications systems, andconsequently the usage of these systems will continue even thoughcommunications systems with new technologies are being introduced. Withwireless technologies, a converter is typically deployed with a basestation radio in order to reconcile technology differences between thebase station radio and the user's wireless terminal. With LMRSoperation, for example, dedicated cabling between radios or radiocontrol consoles are typically required. Furthermore, the user expectsconnectivity between wireless communications systems and wirelinecommunications systems such as the Internet and the public switchedtelephone network (PSTN). There is certainly a need to facilitate theinterconnection of disparate communications systems regardless of theunderlying technology that is serving the user.

BRIEF SUMMARY OF THE INVENTION

The present invention provides methods and apparatus for interconnectingdisparate communications systems. For example, a voice call request thatoriginates from a communications network is directed to a networkinterface. The network interface consequently redirects the call requestto a communications entity, such as a radio or a cellular radio system,that serves the user associated with the call request. The networkinterface may support address translation functionality for identifyingthe communications entity, control conversion functionality forgenerating control and signaling with the communications entity,transmission content conversion functionality for convertingtransmission content during the call, and security functionality forencrypting and decrypting the transmission content. The presentinvention enables network management systems to manage non-networkingcommunications entities (e.g. land mobile radios, public switchingtelephone networks, and personal communications systems) through anetwork. Also, the present invention enables non-networkingcommunications entities to utilize networking routing functions andservices (e.g. directory services). Moreover, the present inventionenables non-networking communications entities to interact withapplications that are being executed on another terminal through thenetwork.

An embodiment is shown for interfacing a communications network with anintelligent network interface (INI) to legacy radios (e.g. land mobileradios), cellular radio systems, and a public switched telephone network(PSTN). The INI comprises a proxy interface, entity control conversion,and entity address translation, security conversion, transmissioncontent conversion. The INI exchanges messages with the network throughthe proxy interface. In order to establish a call to the user'scommunications terminal, the INI selects the appropriate entity (e.g.radio or cellular radio system) in accordance with user-associated dataand entity address conversion.

One embodiment includes a signaling scenario for supporting a wirelessterminal through a land mobile radio (LMR) in which a call requestoriginates from a 3G (third generation) end user terminal served by a 3Gnetwork to a user being served by the LMR. The INI verifies and locatesthe user by accessing user-associated data. The INI consequentlynotifies the appropriate radio interface about necessary characteristicsof the user's wireless terminal and a call is established. The INIconverts voice over IP (VoIP) transmission content to an analog waveformfor transmission from the 3G EUT to the wireless terminal. Conversely,the INI converts an analog waveform to VoIP transmission content fortransmission from the wireless terminal to the 3G EUT.

A variation of the embodiment includes a signaling scenario forsupporting a wireless terminal through a cellular radio system inaccordance with an embodiment of the invention. The INI verifies theuser and locates the cellular radio system that is serving the user. TheINI generates dual tone multi-frequency (DTMF) signaling to the cellularradio system in order to complete the call connection. Subsequently, theINI converts transmission content during the call.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the present invention and theadvantages thereof may be acquired by referring to the followingdescription in consideration of the accompanying drawings, in which likereference numbers indicate like features and wherein:

FIG. 1 shows an architecture of interconnecting disparate wirelesssystems utilizing an intelligent network interface (INI) in accordancewith an embodiment of the invention;

FIG. 2 shows a functional diagram of an intelligent wireless networkinterface in accordance with an embodiment of the invention;

FIG. 3 shows apparatus for an intelligent wireless network interface inaccordance with an embodiment of the invention;

FIG. 4 shows a data structure for storing entity information inaccordance with an embodiment of the invention;

FIG. 5 shows an example of a signaling scenario for supporting awireless terminal through a land mobile radio (LMR) in accordance withan embodiment of the invention; and

FIG. 6 shows an example of a signaling scenario for supporting awireless terminal through a cellular radio system in accordance with anembodiment of the invention.

DETAILED DESCRIPTION OF THE INVENTION

In the following description of the various embodiments, reference ismade to the accompanying drawings which form a part hereof, and in whichis shown by way of illustration various embodiments in which theinvention may be practiced. It is to be understood that otherembodiments may be utilized and structural and functional modificationsmay be made without departing from the scope of the present invention.

FIG. 1 shows an architecture of interconnecting disparate wirelesssystems utilizing intelligent network interface (INI) 103 in accordancewith an embodiment of the invention. End user terminal (EUT) 113, whichis served by 3G (third generation) network 101 over channel 112, cancommunicate with wireless terminal 109, which is served by land mobileradio (LMR) 105 over wireless channel 108 or with wireless terminal 111,which is served by cellular radio system 107 over wireless channel 110.(Cellular radio system 107 is sometimes referred as a “personalcommunications system.”) 3G network 101 can be a wireline network or awireless network. In the embodiment, cellular radio system 107 is afirst generation (1G) or a second generation (2G) wireless system(pre-3G). However, other embodiments can support a subsequent generationof wireless services. In one embodiment, EUT 113 can be one of a varietyof terminals including a 3G wireless terminal or a 3G wireline terminal.EUT 113 can provide different services to the associated user, includingdata services that are associated with the Internet and 3G multimediaservices. Variations of the invention can support other types of legacyradios. (“Legacy radio” pertains to a radio that is not deployed in acellular radio system.) A legacy radio may be dedicated to a user or toa group of users. A major characteristic of a 3G network is the supportof the Internet protocol (IP). Moreover, the present invention cansupport networks that evolve beyond 3G.

If terminal 113 originates a call to either wireless terminal 109 orwireless terminal 111 through 3G network 101, 3G network 101 directs thecall request to INI 103. The call request contains an identification ofthe called wireless terminal and may contain quality of service, cost,and service type requirements. Network 101 has a priori knowledge thatwireless terminal 109 and wireless terminal 111 are associated with INI103. Thus, network 101 directs any related messaging to INI 103 with adesignated IP address. In the embodiment, network 101 maintains thisrelationship through a data structure that is updated by a serviceprovider of network 101. A variation of the embodiment utilizes aregistration procedure in which a corresponding entry for wirelessterminal 109 or wireless terminal 111 is updated whenever a status ofthe wireless terminal changes. INI 103 maintains user-associated dataabout each user (which will be explained in more detail in the contextof FIG. 2) in order to direct the call to wireless terminal 109 (thoughpath 104 and legacy radio 105) or to wireless terminal 111 (through path106 and cellular radio system 107).

If wireless terminal 109 or wireless terminal 111 originates a call towireless terminal 113, INI 103 directs the call to network 101 throughpath 102. In the embodiment, network 101 maintains user-associated dataassociated with terminal 113 in order to route the call.

Network management system (NMS) 115 manages 3G network 101 throughconnection 114 using a network management protocol. NMS 115 is a systemof equipment used for monitoring, controlling, and managing acommunications network. The network management protocol enables NMS 115to support functions at a network management layer. Typically, NMS 115supports configuration management (deals with installing, initializing,“boot” loading, modifying and tracking configuration parameters ofnetwork hardware and software), fault location and repair management(indicates faults with equipment and facilities and supports repairingthe faults), security management tools (allows the network manager torestrict access to various resources in the network), performancemanagement tools (provides real-time and historical statisticalinformation about the network's operation), and accounting managementapplications (helps operators to allocate costs of various networkresources).

The present invention extends the span of NMS 115 to include LMR 105 andcellular radio system 107. In the embodiment, NMS 115 verifies theoperation of LMR 105 by activating LMS 105 and receiving statusinformation from LMS 105. NMS 115 utilizes the network managementprotocol (e.g. signaling network management protocol (SNMP)), and INI103 converts the corresponding commands (e.g. activating LMR 105) into aformat that is compatible with LMR 105. (In particular, proxy interface201, which is discussed in the context of FIG. 2, does the protocolconversion.) Equipment and configuration information about LMR 105 canreside at either INI 103 or NMS 115. The embodiment also extends thespan of NMS 115 to cellular radio system 107. NMS 115 can test radiosand facilities associated with radio base stations that are controlledby cellular radio system 107.

FIG. 2 shows a functional diagram of intelligent wireless networkinterface 103 in accordance with an embodiment of the invention. Proxyinterface 201 provides an interface to network 101 in order to receivemessaging to and from network 101. Messaging associated with a callincludes signaling messages as well as transmission content such asvoice over IP (VoIP). The transmission content can support voice, data,or multimedia information that is transported during a call betweenusers. (Messaging is explained in more detail in the context of FIGS. 5and 6.) In the embodiment, proxy interface 201 is implemented byutilizing Joint Tactical Radio System (JTRS) software communicationsarchitecture (SCA). SCA is an open, standardized architecture thatsupports different network protocols including emerging widebandnetworking capabilities for voice, data, and video. (One can refer tothe Support and Rationale Document for the Software CommunicationsArchitecture Specification, MSRC-5000 SRD V1.2, Dec. 21, 2000 that isavailable at http://wwwjtrs.saalt.army.mil.)

Software for implementing entity control conversion 215, transmissioncontent conversion 217, security conversion 218, entity addresstranslation 221, entity selection 231, and interfaces 205, 207, 213,211, and 209 are based upon framework 203. (Framework 203 is a set ofprefabricated software building blocks.)

User-associated data 219 contains data about each user that is served byINI 103 and is explained in more detail in the context of FIG. 4.User-associated data 219 contains the entity address 403 that isassociated with a user. Entity address translation 221 uses data from219 in order to direct a call through entity selection 231 to anappropriate communications entity (associated with legacy radio Ainterface 205, legacy radio B interface 207, public switching telephonenetwork (PSTN) interface 213, cellular radio system A interface 209, orcellular radio system B interface 211). Interfaces 205, 207, 213, 209,and 211 include software and hardware to support the required physicallayer such as appropriate voltage levels and connector pin arrangements.The appropriate communications entity (that can serve the user and maybe a radio such as LMR 105 or a network such as cellular radio system107) is connected to an interface in order to communicate to a wirelessterminal (e.g. 109 or 111) or to a wireline terminal (e.g. through PSTNinterface 213).

Transmission content conversion 217 converts transmission content (e.g.VoIP) from network 101 into a format (such as an analog waveform or 64kbps Mu Law pulse code modulation) that is amenable for the target radiothat interfaces to INI 103 through paths 214, 218, 220, 222, and 226.(“Transmission content” pertains to the content being sent on thecommunications connection between EUT 113 and the wireless terminalbeing served by INI 103. “User-associated data” pertains to data aboutthe corresponding terminal that is served by INI 103. An example of“user-associated data” is data rate capability of the wireless terminal109.) Security conversion 218 provides encryption and decryption oftransmission content in order to provide the necessary degree ofsecurity for communications between terminals. Entity control conversion215 converts signaling from network 101 into a control signal that isamenable to the target radio or creates a control signal that isassociated with an event during the call through paths 212, 216, 224,228, and 230. (Operation of entity control conversion is discussed inmore detail in the context of the examples in FIGS. 5 and 6.)

Entity control conversion 215, transmission content conversion 217,security conversion 218, and entity address translation 221 interactwith proxy interface 201 over path 202 in order to obtain messaging toand from network 101. Also, proxy interface 201, entity controlconversion 215, transmission content conversion 217, security conversion218, and entity address translation 221 interact with user-associateddata 219 over path 204.

FIG. 3 shows apparatus for INI 103 in accordance with an embodiment ofthe invention. Data port 301 (corresponding to proxy interface 201 inFIG. 2) receives and sends messages (both transmission content andsignaling messages) between INI 103 and network 101. Data ports 303 and305 interface to communications entities that are supported by INI 103and correspond to interfaces 205, 207, 213, 209, and 211. Processor 307executes computer executable instructions from memory 309 through path310 (corresponding to path 204) in order to support the entity controlconversion 215, security conversion 218, entity address translation 221,entity selection 231, and interfaces 205, 207, 213, 209, and 211. Also,memory 309 stores data structure 419 in order to support user-associateddata 219.

Processor 307 interacts with data port 301 over connection 302(corresponding to path 202). Processor 307 interacts with data port 303over connection 306 (corresponding to paths 212, 216, 224, 228, or 230)and connection 304 (corresponding to paths 214, 218, 220, 222, and 226).Processor 307 interacts with data port 305 over connection 308 andconnection 312.

FIG. 4 shows data structure 419 for storing user-associated data 219 inaccordance with an embodiment of the invention. Data structure 419comprises a plurality of records, each including user ID field 401,entity address field 403, and attributes field 405. User ID field 401identifies the user and may be the user's telephone number or IPaddress. Entity address field 403 identifies the communications entity(e.g. legacy radio 105 or cellular radio system 107) that the user isassociated with. User attributes field 405 is a collection of attributes(e.g. type of service, priority, quality of service, cost, and data ratecapability) that is associated with the user. In the embodiment, userattributes are provisioned by a service provider through data port 301and processor 307 to memory 309, which contains data structure 419.Processor 307 accesses data structure 419 (which is contained in memory309 in the embodiment) to determine how to process a call request thatis associated with the user (corresponding to user ID 401). The examplesin FIGS. 5 and 6 illustrate call processing in greater detail.

FIG. 5 shows an example of a signaling scenario for supporting wirelessterminal 109 through land mobile radio (LMR) 105 in accordance with anembodiment of the invention. End user terminal (EUT) 113 initiates thecall by sending session request message 501 to network 101. Network 101consequently sends session request message 503 to INI 103 (in particularto proxy interface function 201) corresponding to a designated IPaddress. In the embodiment, network 103 is connected to only oneintelligent network interface (INI 103). However, in alternativeembodiments, network 103 may maintain information that maps thedestination user to a corresponding intelligent network interface.Session request messages 501 and 503 contain parameters (data fields)that include an identification of wireless terminal 109 and a servicetype (e.g. video with analog). Additionally, session request 501 and 503can include a requested quality of service (QoS) level, a minimum QoSlevel, cost limitations associated with the call, and data ratecapability. With verify user action 505, proxy interface function 201verifies that the parameters are consistent with user-associated data219.

For example, the identification of the user in session request message503 should match user ID 401 in one of the entries in data structure419. Also, the service type contained in session request message 503should be consistent with user attributes 405. If proxy interface 201verifies the user (associated with wireless terminal 109), proxyinterface 201 returns accept message 507 to network 101. However, ifproxy interface 201 determines that the user identity does not match anyuser being served by INI 103 or there is an inconsistency between thedata fields in session request message 503 and user-associated data 219,then proxy interface 201 returns a reject message to network 101.(However, with an alternative of the embodiment, INI 103 sends anegotiation message to network 101 with an alternative parameter value,e.g. an alternative service type or data rate, that is consistent withthe user attributes. If network 101 determines that the alternativeparameter value is acceptable for EUT 113, network 101 returns an acceptmessage to proxy interface 201 to continue the processing of the call.)

With locate entity action 509 as performed by address conversionfunction 221, address conversion function 221 obtains entity address 403that is contained in the appropriate entry of data structure 419(corresponding to user-associated data 219) and locates communicationsentity (LMR) 105 that serves wireless terminal 109. LMR 105 is connectedto radio interface 205. In the example shown in FIG. 5, thecommunications entity is a radio. However, the present inventionsupports communications entities that include cellular radio networks(as illustrated in the signaling scenario in FIG. 6), public switchedtelephone networks (PSTN), and data networks (e.g. an Internet network).Once LMR 105 is identified, address conversion function 221 instructscontrol conversion 215 by action 511 to notify radio interface 205(which interfaces to radio 105) about physical characteristics of radio105 with notify action 513. The physical characteristics include afrequency of the radio and a format of the transmission content, e.g. ananalog waveform. The operation of radio 105 is verified by status 514.Consequently, control conversion function 215 sends proceed message 515to network 101 through network proxy interface 103.

The communication between EUT 113 and wireless terminal 109 commenceswith talk message 517. At this point of time, INI 103 has completed thecall connection between EUT 113 and wireless terminal 109 through radio105. Consequently, control conversion function 215 generates push totalk (PTT) command 519 to radio 105 through radio interface 205.

In one embodiment, EUT 113 sends transmission content using a voice overIP (VoIP) format; however, wireless terminal 109 can only process ananalog format. Thus, VoIP transmission content 521 is converted toanalog waveform 523 by transmission content conversion function 217. Inthe embodiment, radio 105 and wireless terminal 109 operate in halfduplex operation, i.e. both radio 105 and wireless terminal 109 do nottransmit at the same time. When wireless terminal 109 is transmitting,analog waveform 527 is converted to VoIP transmission content 529 inorder to be compatible with the operation of EUT 113. In the embodiment,transmission content conversion 217 assesses the activity between EUT113 and wireless terminal 109. When transmission content conversionfunction 217 determines that EUT 113 is talking, function 217 notifiescontrol conversion function 215 through action 525. When transmissioncontent conversion function 217 determines that wireless terminal 109 istalking, function 217 notifies control conversion function 215 throughaction 531. In an alternative embodiment, when wireless terminal 109transmits, a PTT command is sent from wireless terminal 109 to controlfunction 215, which in turn sends a talk message to network 103.

Disconnect message 533 indicates that EUT 113 has disconnected from thecall. Control conversion receives message 533 through proxy interface201 and consequently sends disconnect message 535 to radio 105 throughradio interface 205.

The embodiment also supports a call that is originated from wireless 109to EUT 113. With such a scenario, INI 103 sends a session requestmessage to network 101 with a user identification corresponding to EUT113. Network 101 locates EUT 113 in order to complete the call to EUT113. The scenario is similar to the scenario shown in FIG. 5. However,the address conversion function 221 does not locate the communicationsentity that is associated with wireless terminal 109 because wirelessterminal 109 has explicitly identified itself through the call request.

With FIG. 6, EUT 113 originates a call to wireless terminal 111, whichis currently served by cellular radio system 107. Cellular radio system107 is connected to radio interface 209. As with the example in FIG. 5,data structure 419 (corresponding to user-associated data function 219)comprises an entry corresponding to wireless terminal 111. The entrycomprises entity address field 403 that corresponds to an identificationof cellular radio system 107. FIG. 6 shows an example of a signalingscenario for supporting wireless terminal 111 through cellular radiosystem 107 in accordance with an embodiment of the invention. Signalingmessages 601, 603, 605, 607, and 609 correspond to signaling messages501, 503, 505, 507, and 509 as shown in FIG. 5. In action 611, addressconversion function 221 instructs control conversion function 215 togenerate dual tone multi-frequency (DTMF) signal 613 through radiointerface 209 to cellular radio system 211. In the embodiment, DTMFsignal 613 corresponds to a telephone number of wireless terminal 111.Signal 613 initiates cellular radio system 107 to page wireless terminal111. When wireless terminal 111 responds to paging, cellular radiosystem 107 generates status indication 614 through radio interface 209to control conversion function 215. Consequently, control conversionfunction 215 sends proceed message 615 through proxy interface 201 tonetwork 101 in order that communications is established between EUT 113and wireless terminal 111. Consequently, a call connection is completedbetween EUT 113 and wireless terminal 111 through cellular radio system107.

Transmission content is sent between EUT 113 and wireless terminal 111.EUT 113 transmits and receives VoIP transmission content 621 throughnetwork 101 and proxy interface 201 in conjunction with transmissioncontent conversion function 217.

Transmission content conversion function 217 converts VoIP transmissioncontent 621 to pulse code modulation (PCM) transmission content 623 fortransmission to wireless terminal 111 and converts PCM transmissioncontent 623 to VoIP transmission content 621 for transmission fromwireless terminal 111. Message 633, which indicates that EUT 113 hasterminated the call, is sent through network 101 and proxy interface 201to control conversion function 215. Consequently, control conversion 215sends message 635 to cellular radio system 107 in order to terminate thecall.

Other embodiments may support other variations of transmission content623 (that may be associated with a voice waveform of a user), includingcode excited linear prediction (CELP, e.g. Standard G.728), adaptivedifferential pulse code modulation (ADPCM, e.g. Standard G.726) andvoice over IP (VoIP). Moreover, variations of the embodiment may supporta call in which transmission content does not represent a voice waveformof a user. In such a case, the call is often referenced as a “datacall.” For example, INI 103 may support an interface to an X.25 network.

FIGS. 5 and 6 illustrate signaling messages for a setting up andmaintaining a call.

Moreover, INI 103 enables non-networking communications entities (e.g.LMR 105) to exploit networking protocols, including differentiatedservices (DiffServ), multiprotocol label switching (MPLS), multi-levelpriority protocol (MLPS), and bandwidth brokers. Networking protocolstypically enable network 101 to support a designated quality of service(QoS) level when routing traffic (e.g. data packets) through network 101to terminal 113 during the call. In the embodiment, MPLS enables datapackets to have added labels so that data packets are forwarded alongpre-constructed label-switched paths (LSP's) by routers that aremodified to switch MPLS frames in network 101. In the embodiment,DiffServ typically utilizes a DiffServ code point (DSCP) that indicatesdifferentiated traffic handling corresponding to different QoS levels,in which a QoS level is associated with a data flow of a call.

In the embodiment, proxy interface 201 adds a label for a MPLS frame andincludes a DSCP for a data packet if supporting DiffServ. Proxyinterface 201 utilizes a QoS level as indicated by network 101 in a dataflow that is sent between terminal 113 and terminal 109 or betweenterminal 113 and terminal 111.

In the embodiment, network 101 may multiplex a plurality of independentapplication flows for terminal 113 that are based upon port numbers. Aport number is typically included in a data packet and is associatedwith an application that is executing on terminal 113. An application isa software program that executes on terminal 113 (e.g. a spreadsheet,communications package, or graphics program). An IP address is assignedto terminal 113 and determined by an identification of terminal 113 andthe designated application. If terminal 109 and terminal 113 arecommunicating with each other, terminal 113 may execute a VoIPapplication in order to support voice communications. However, theembodiment supports other applications, including e-mail exchanges andfile transfer services. In the embodiment, proxy interface 201 utilizesan appropriate port number in order to support a service that isassociated with communications between terminal 113 and terminal 109 andbetween terminal 113 and terminal 111.

The embodiment also supports non-call associated services, includingdirectory services for terminals 109 and 111. A directory service isprovided by directory server 117 through facility 116. Server 117determines an IP address that is assigned to terminal 113 when queriedwith identifying attributes of a user, e.g. a user's identification andapplication type. Terminal 109 or terminal 111 sends a directory requestto INI 103. Proxy interface 201 translates the request in order to queryserver 117 and sends the translated request to an IP address of server117.

As can be appreciated by one skilled in the art, a computer system withan associated computer-readable medium containing instructions forcontrolling the computer system can be utilized to implement theexemplary embodiments that are disclosed herein. The computer system mayinclude at least one computer such as a microprocessor, digital signalprocessor, and associated peripheral electronic circuitry.

While the invention has been described with respect to specific examplesincluding presently preferred modes of carrying out the invention, thoseskilled in the art will appreciate that there are numerous variationsand permutations of the above described systems and techniques that fallwithin the spirit and scope of the invention as set forth in theappended claims.

1. A method for a network management system (NMS) managing acommunications entity through a network interface, the NMS associatedwith a communications network, the method comprising: (a) receiving,from the NMS through the communications network, a network managementrequest conforming to a network management protocol; (b) translating thenetwork management request between the communications network and thecommunications entity to a translated request that is compatible withthe communications entity; (c) determining whether the translatedrequest is intended for the communications entity; and (d) in responseto (c), sending the translated request from the NMS through thecommunications network to activate the communications entity.
 2. Anetwork interface for supporting a network management system (NMS) tomanage a communications entity through a network interface, the NMSassociated with a communications network, the network interfacecomprising: at least one data port that interfaces to the communicationsnetwork and to the communications entity; and a processor communicatingthrough the data port to the communications network and to thecommunications entity, the processor configured to perform: (a)receiving from the NMS through the communications network a networkmanagement request conforming to a network management protocol; (b)translating the network management request between the communicationsnetwork and the communications entity to a translated request that iscompatible with the communications entity; (c) determining whether thetranslated request is intended for the communications entity; and (d) inresponse to (c), sending the translated request from the NMS through thecommunications network to activate the communications entity.
 3. Themethod of claim 1, the communications entity being one of a PTT radionetwork and a cellular radio network and (b) including translating asignaling protocol between the communications network to either the PTTradio network or the cellular radio network to support a call.
 4. Thenetwork interface of claim 2, the communications entity being one of aPTT radio network and a cellular radio network and (b) includingtranslating a signaling protocol between the communications network toeither the PTT radio network or the cellular radio network to support acall.
 5. The method of claim 1, further comprising: (e) determining afault in the communications entity.
 6. The method of claim 5, furthercomprising: (f) repairing the fault in the communications entity.
 7. Themethod of claim 1, further comprising: (e) restricting access to aresource of the communications entity.
 8. The method of claim 1, furthercomprising: (e) managing at least one configuration parameter that isassociated with the communications entity.
 9. The method of claim 8,wherein (e) comprises: (e)(i) modifying the at least one configurationparameter.
 10. The method of claim 8, wherein (e) comprises: (e)(i)installing the at least one configuration parameter.
 11. The method ofclaim 8, wherein (e) comprises: (e)(i) tracking the at least oneconfiguration parameter.
 12. The method of claim 1, further comprising:(e) in response to (d), receiving status information about thecommunications entity.
 13. The method of claim 1, further comprising:(e) determining a performance measurement associated with thecommunications entity.
 14. A computer-readable medium havingcomputer-executable components comprising: (a) receiving, from a networkmanagement system (NMS) through a communications network, a networkmanagement request for a communications entity conforming to a networkmanagement protocol; (b) translating the network management requestbetween the communications network and the communications entity to atranslated request that is compatible with the communications entity;(c) determining whether the translated request is intended for thecommunications entity; and (d) in response to (c), sending thetranslated request from the NMS through the communications network toactivate the communications entity.